linux.debian.bugs.dist
[Top] [All Lists]

Bug#385454: [Pkg-mythtv-maintainers] Bug#385454: ivtv-source: package pr

Subject: Bug#385454: [Pkg-mythtv-maintainers] Bug#385454: ivtv-source: package provides several unwanted /lib/modules/$KERNEL/modules-files
From: Michael Prokop
Date: Thu, 31 Aug 2006 16:10:08 +0200
Newsgroups: linux.debian.bugs.dist
* Ian Campbell <ijc@xxxxxxxxxxxxxx> [20060831 15:15]:
> On Thu, 2006-08-31 at 13:29 +0200, Michael Prokop wrote:
> > If I build the ivtv package against my kernel the final .deb
> > includes several modules-files which shouldn't be part of the deb:

> Strange, that doesn't happen here.

> Do you have a build log? One from a manual or module-assistant build
> would do.

Sure, see attached buildlog.

The command I used for building was:

# KPKG_DEST_DIR=/raid/Grml/kernel/ module-assistant -f -l       \
  '2.6.17-grml' -k /raid/Grml/kernel/linux-2.6.17-grml build ivtv

> By "manual" do you mean with make-kpkg or some other by-hand method?

By manual I mean building via 'debian/rules binary-modules'.

> Does the -grml suffix mean anything in particular in terms of patches
> applied or is the kernel built from kernel.org source?

It's the kernel used in the grml live-cd system (see
grml.org/kernel/ for details). It's based on kernel.org sources with
some additional patches applied, but that shouldn't matter IMO.

> I only tested with m-a against a Debian kernel package. I'll try against
> a self built kernel now.

In case this might be important (it often is when kernel source
packages are broken):

Do you build the package against the currently running kernel?
Because I'm building the module against a kernel version which does
not match the currently running one.

thx && regards,
-mika-
-- 
 ,'"`.         http://www.michael-prokop.at/
(  grml.org -» Linux Live-CD for texttool-users and sysadmins
 `._,'                                         www.grml.org/">http://www.grml.org/

Attachment: ivtv-source.buildlog.2.6.17-grml.1157030230
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>
Privacy Policy